| Package | ForgePatientChart.0830 |
| Type | StructureDefinition |
| Id | Id |
| FHIR Version | R4 |
| Source | https://simplifier.net/resolve?scope=ForgePatientChart.0830@0.1.0&canonical=http://telus.com/fhir/patientChart/StructureDefinition/profile-observation-lab |
| Url | http://telus.com/fhir/patientChart/StructureDefinition/profile-observation-lab |
| Status | draft |
| Name | LabObservation |
| Title | Lab Observation |
| Experimental | False |
| Authority | hl7 |
| Type | Observation |
| Kind | resource |
| StructureDefinition | |
http://telus.com/fhir/patientChart/StructureDefinition/profile-composition  | Composition Patient Chart |
No resources found
FHIR{
"resourceType" : "StructureDefinition",
"id" : "profile-observation-lab-patientchart",
"url" : "http://telus.com/fhir/patientChart/StructureDefinition/profile-observation-lab",
"name" : "LabObservation",
"title" : "Lab Observation",
"status" : "draft",
"fhirVersion" : "4.0.1",
"mapping" : [
{
"identity" : "workflow",
"uri" : "http://hl7.org/fhir/workflow",
"name" : "Workflow Pattern"
},
{
"identity" : "sct-concept",
"uri" : "http://snomed.info/conceptdomain",
"name" : "SNOMED CT Concept Domain Binding"
},
{
"identity" : "v2",
"uri" : "http://hl7.org/v2",
"name" : "HL7 v2 Mapping"
},
{
"identity" : "rim",
"uri" : "http://hl7.org/v3",
"name" : "RIM Mapping"
},
{
"identity" : "w5",
"uri" : "http://hl7.org/fhir/fivews",
"name" : "FiveWs Pattern Mapping"
},
{
"identity" : "sct-attr",
"uri" : "http://snomed.org/attributebinding",
"name" : "SNOMED CT Attribute Binding"
}
],
"kind" : "resource",
"abstract" : false,
"type" : "Observation",
"baseDefinition" : "http://hl7.org/fhir/StructureDefinition/Observation",
"derivation" : "constraint",
"differential" : {
"element" : [
{
"id" : "Observation",
"path" : "Observation",
"comment" : "Alignment: There is a profile for Core-CA; no lab observation profile defined in PS-CA o PS-ON (as at July 2022)\r\n\r\nUsed for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc."
},
{
"id" : "Observation.id",
"path" : "Observation.id",
"mustSupport" : true
},
{
"id" : "Observation.meta",
"path" : "Observation.meta",
"mustSupport" : true
},
{
"id" : "Observation.meta.lastUpdated",
"path" : "Observation.meta.lastUpdated",
"mustSupport" : true
},
{
"id" : "Observation.meta.source",
"path" : "Observation.meta.source",
"mustSupport" : true
},
{
"id" : "Observation.meta.profile",
"path" : "Observation.meta.profile",
"mustSupport" : true
},
{
"id" : "Observation.text",
"path" : "Observation.text",
"requirements" : "DISCUSSION REQUIRED TO CONFIRM",
"mustSupport" : true
},
{
"id" : "Observation.identifier",
"path" : "Observation.identifier",
"comment" : "Usage Note: This should be populated if known. This is supported by OLIS"
},
{
"id" : "Observation.basedOn",
"path" : "Observation.basedOn",
"comment" : "Usage Note: This should be populated if known. This is mandatory in the OLIS specification\r\n\r\nReferences SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository."
},
{
"id" : "Observation.partOf",
"path" : "Observation.partOf",
"requirements" : "Usage Note: For now, this is out of scope. This could be a lab result that is tied to a procedure, however it is very uncommon to have this linkage within the EMR. eg specimen, observation after the fact is NOT a part of; surgery observations. \r\n\r\nMA: C3 says yes it is available; Can access it via Task.ID or Problem.ID or Allergy.ID etc. BUT, if done at task level, other non-relavent observations could be captured along with that. (ex: height for diabeties). ie: data is being captured but it could very likely be 'noisy'."
},
{
"id" : "Observation.partOf.reference",
"path" : "Observation.partOf.reference",
"mustSupport" : true
},
{
"id" : "Observation.partOf.display",
"path" : "Observation.partOf.display",
"mustSupport" : true
},
{
"id" : "Observation.status",
"path" : "Observation.status",
"mustSupport" : true
},
{
"id" : "Observation.category",
"path" : "Observation.category",
"min" : 1,
"max" : "1",
"fixedCodeableConcept" : {
"text" : "laboratory"
},
"mustSupport" : true
},
{
"id" : "Observation.category.coding",
"path" : "Observation.category.coding",
"mustSupport" : true
},
{
"id" : "Observation.category.coding.system",
"path" : "Observation.category.coding.system",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Observation.category.coding.code",
"path" : "Observation.category.coding.code",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Observation.category.coding.display",
"path" : "Observation.category.coding.display",
"mustSupport" : true
},
{
"id" : "Observation.category.text",
"path" : "Observation.category.text",
"mustSupport" : true
},
{
"id" : "Observation.code",
"path" : "Observation.code",
"comment" : "Usage Note: The sending systems will always send text and where possible will also send a codified value. These are not always available. Local codes shoudl be converted to LOINC where possible. \r\n\r\nEMR API:\r\nLOINC (example)\r\nhttp://hl7.org/fhir/ValueSet/observation-codes >1000 codes\r\nMA: loinc (most common), ICD-9, snomed,type code, atc class, workload, and no codes as well\r\nPSS:\r\nMS: PCLOCD, ICD-10\r\n\r\n*All* code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation.",
"mustSupport" : true,
"binding" : {
"strength" : "preferred"
}
},
{
"id" : "Observation.code.coding",
"path" : "Observation.code.coding",
"mustSupport" : true
},
{
"id" : "Observation.code.coding.system",
"path" : "Observation.code.coding.system",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Observation.code.coding.code",
"path" : "Observation.code.coding.code",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Observation.code.coding.display",
"path" : "Observation.code.coding.display",
"mustSupport" : true
},
{
"id" : "Observation.code.text",
"path" : "Observation.code.text",
"comment" : "Usage Note: If the lab result is just an OBX, with NTE's, there is no specific code; this must be populated as \"lab note\".\r\n\r\nPSS: Observation Name (text) \r\n\r\nery often the text is the same as a displayName of one of the codings.",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Observation.subject",
"path" : "Observation.subject",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Observation.subject.reference",
"path" : "Observation.subject.reference",
"mustSupport" : true
},
{
"id" : "Observation.subject.display",
"path" : "Observation.subject.display",
"mustSupport" : true
},
{
"id" : "Observation.encounter",
"path" : "Observation.encounter",
"comment" : "Usage Note: In some cases the lab observation can be linked to the encoutner in the EMR. Example: Prenatal urinalysis results are often linked to an encounter. \r\nUsage Note DW: Use of this element may vary by implementation/clent agreements\r\nUsage Note: This is not in scope for OLIS\r\n\r\nThis will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission laboratory tests).",
"mustSupport" : true
},
{
"id" : "Observation.encounter.reference",
"path" : "Observation.encounter.reference",
"mustSupport" : true
},
{
"id" : "Observation.encounter.display",
"path" : "Observation.encounter.display",
"comment" : "Usage Note: Use of this data element will vary by implementation.\r\n\r\nThis is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.",
"mustSupport" : true
},
{
"id" : "Observation.effective[x]",
"path" : "Observation.effective[x]",
"comment" : "Usage Note: Manual lab entries always have a date which is the date used; may not distinguish between collection date and observation date\r\n**** Add data absent reason extension as per core\r\n\r\n At least a date should be present unless this observation is a historical report. For recording imprecise or \"fuzzy\" times (For example, a blood glucose measurement taken \"after breakfast\") use the [Timing](datatypes.html#timing) datatype which allow the measurement to be tied to regular life events.",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Observation.performer",
"path" : "Observation.performer",
"comment" : "Usage Note: If the name of the performer (eg Lifelabs or Dr. Smith) is known this should be sent.\r\n\r\nReferences SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.",
"mustSupport" : true
},
{
"id" : "Observation.performer.display",
"path" : "Observation.performer.display",
"mustSupport" : true
},
{
"id" : "Observation.value[x]",
"path" : "Observation.value[x]",
"comment" : "Usage Rule: This must be sent where known; it is possible that there are component values but no top level values and therefore this is not mandatory.\r\nUsage Note: These values must be represented exactly as they are from the source. eg Labs may send a string such as \"pending\". \r\nUsage Note: If labs have sent notes associated with the observation, they should be sent as part of the value as a string. This may be in the OBX or the NTE assocaited with the OBX. \r\nAlignment: Core-CA only supports codeableConcept and quantity \r\n\r\nAn observation may have; 1) a single value here, 2) both a value and a set of related or component values, or 3) only a set of related or component values. If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the [Notes section](observation.html#notes) below.",
"mustSupport" : true
},
{
"id" : "Observation.dataAbsentReason",
"path" : "Observation.dataAbsentReason",
"comment" : "Usage Note: A value of \"temp-unknown\" may be used for pending results in the EMR (status=registered). This could occur with a panel that has returned some final results with others that are showing as outstanding\r\n\r\nNull or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be \"detected\", \"not detected\", \"inconclusive\", or \"specimen unsatisfactory\". \n\nThe alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code \"error\" could be used when the measurement was not completed. Note that an observation may only be reported if there are values to report. For example differential cell counts values may be reported only when > 0. Because of these options, use-case agreements are required to interpret general observations for null or exceptional values.",
"mustSupport" : true
},
{
"id" : "Observation.dataAbsentReason.text",
"path" : "Observation.dataAbsentReason.text",
"comment" : "Usage Note: This should be populated with the value from the lab as stored in the EMR, eg \"pending\" when a data absent reason of \"temp-unknown\" is used\r\n\r\nVery often the text is the same as a displayName of one of the codings.",
"mustSupport" : true
},
{
"id" : "Observation.interpretation",
"path" : "Observation.interpretation",
"mustSupport" : true
},
{
"id" : "Observation.interpretation.coding",
"path" : "Observation.interpretation.coding",
"mustSupport" : true
},
{
"id" : "Observation.interpretation.coding.system",
"path" : "Observation.interpretation.coding.system",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Observation.interpretation.coding.code",
"path" : "Observation.interpretation.coding.code",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Observation.interpretation.text",
"path" : "Observation.interpretation.text",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Observation.note",
"path" : "Observation.note",
"comment" : "Usage Note: Annotations added by the clinician. Notes from the lab are conveyed as separate observations\r\n\r\nMay include general statements about the observation, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation.",
"mustSupport" : true
},
{
"id" : "Observation.note.author[x]",
"path" : "Observation.note.author[x]",
"mustSupport" : true
},
{
"id" : "Observation.note.time",
"path" : "Observation.note.time",
"mustSupport" : true
},
{
"id" : "Observation.note.text",
"path" : "Observation.note.text",
"mustSupport" : true
},
{
"id" : "Observation.method",
"path" : "Observation.method",
"comment" : "Usage Note: If present in the lab result this will be passed on as is.\r\n\r\nOnly used if not implicit in code for Observation.code.",
"mustSupport" : true
},
{
"id" : "Observation.method.coding",
"path" : "Observation.method.coding",
"mustSupport" : true
},
{
"id" : "Observation.method.text",
"path" : "Observation.method.text",
"mustSupport" : true
},
{
"id" : "Observation.specimen",
"path" : "Observation.specimen",
"comment" : "Usage Note: This is not supported today in the EMR's; if labs begin to send results in FHIR, this may come into scope in the future\r\n\r\nShould only be used if not implicit in code found in `Observation.code`. Observations are not made on specimens themselves; they are made on a subject, but in many cases by the means of a specimen. Note that although specimens are often involved, they are not always tracked and reported explicitly. Also note that observation resources may be used in contexts that track the specimen explicitly (e.g. Diagnostic Report)."
},
{
"id" : "Observation.referenceRange",
"path" : "Observation.referenceRange",
"mustSupport" : true
},
{
"id" : "Observation.referenceRange.low",
"path" : "Observation.referenceRange.low",
"mustSupport" : true
},
{
"id" : "Observation.referenceRange.high",
"path" : "Observation.referenceRange.high",
"mustSupport" : true
},
{
"id" : "Observation.referenceRange.appliesTo",
"path" : "Observation.referenceRange.appliesTo",
"comment" : "Usage Note: This will be present if received from the lab and if stored in the EMR\r\n\r\nThis SHOULD be populated if there is more than one range. If this element is not present then the normal population is assumed.",
"mustSupport" : true
},
{
"id" : "Observation.referenceRange.appliesTo.coding",
"path" : "Observation.referenceRange.appliesTo.coding",
"mustSupport" : true
},
{
"id" : "Observation.referenceRange.appliesTo.coding.system",
"path" : "Observation.referenceRange.appliesTo.coding.system",
"mustSupport" : true
},
{
"id" : "Observation.referenceRange.appliesTo.coding.code",
"path" : "Observation.referenceRange.appliesTo.coding.code",
"mustSupport" : true
},
{
"id" : "Observation.referenceRange.appliesTo.coding.display",
"path" : "Observation.referenceRange.appliesTo.coding.display",
"mustSupport" : true
},
{
"id" : "Observation.referenceRange.appliesTo.text",
"path" : "Observation.referenceRange.appliesTo.text",
"mustSupport" : true
},
{
"id" : "Observation.referenceRange.text",
"path" : "Observation.referenceRange.text",
"mustSupport" : true
},
{
"id" : "Observation.hasMember",
"path" : "Observation.hasMember",
"comment" : "Usage Note: This is not in scope for OLIS; this is in scope for IPS\r\nUsage: PSS: Looked at an example to see if this is used (OBX-4 relationship) and cannot determine this relationship\r\n\r\n\r\nWhen using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases. For a discussion on the ways Observations can assembled in groups together, see [Notes](observation.html#obsgrouping) below. Note that a system may calculate results from [QuestionnaireResponse](questionnaireresponse.html) into a final score and represent the score as an Observation."
},
{
"id" : "Observation.derivedFrom",
"path" : "Observation.derivedFrom",
"comment" : "Usage Note: This may be considered for future use as it is rare that a physician/EMR would link observations back to the original document.\r\n\r\nAll the reference choices that are listed in this element can represent clinical observations and other measurements that may be the source for a derived value. The most common reference will be another Observation. For a discussion on the ways Observations can assembled in groups together, see [Notes](observation.html#obsgrouping) below."
},
{
"id" : "Observation.component",
"path" : "Observation.component",
"comment" : "Discussion required: May be some linking in MedAccess. \r\nUsage Note: This is not supported by OLIS\r\n\r\nFor a discussion on the ways Observations can be assembled in groups together see [Notes](observation.html#notes) below.",
"mustSupport" : true
},
{
"id" : "Observation.component.code",
"path" : "Observation.component.code",
"comment" : "Example from MA:\r\n<OBX.3>\r\n<CE.1>6690-2</CE.1>\r\n<CE.2>WBC</CE.2>\r\n<CE.3/>\r\n<CE.4/>\r\n<CE.5/>\r\n<CE.6/>\r\n</OBX.3>\r\n*All* code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation.",
"mustSupport" : true
},
{
"id" : "Observation.component.code.coding",
"path" : "Observation.component.code.coding",
"max" : "1",
"mustSupport" : true
},
{
"id" : "Observation.component.code.coding.system",
"path" : "Observation.component.code.coding.system",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Observation.component.code.coding.code",
"path" : "Observation.component.code.coding.code",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Observation.component.code.coding.display",
"path" : "Observation.component.code.coding.display",
"mustSupport" : true
},
{
"id" : "Observation.component.code.text",
"path" : "Observation.component.code.text",
"comment" : "Conformance: This must be present when known\r\n\r\nVery often the text is the same as a displayName of one of the codings.",
"mustSupport" : true
},
{
"id" : "Observation.component.interpretation",
"path" : "Observation.component.interpretation",
"mustSupport" : true
},
{
"id" : "Observation.component.interpretation.coding",
"path" : "Observation.component.interpretation.coding",
"mustSupport" : true
},
{
"id" : "Observation.component.interpretation.text",
"path" : "Observation.component.interpretation.text",
"mustSupport" : true
},
{
"id" : "Observation.component.referenceRange",
"path" : "Observation.component.referenceRange",
"comment" : "MA: Display range, lower range, upper range. What is the display range? Do we share this? If YES we need an extension. Definitiion: the range that you want to set as a ideal/base reference\r\n\r\nMost observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.",
"contentReference" : "http://hl7.org/fhir/StructureDefinition/Observation#Observation.referenceRange",
"mustSupport" : true
},
{
"id" : "Observation.component.referenceRange.low",
"path" : "Observation.component.referenceRange.low",
"mustSupport" : true
},
{
"id" : "Observation.component.referenceRange.high",
"path" : "Observation.component.referenceRange.high",
"mustSupport" : true
},
{
"id" : "Observation.component.referenceRange.text",
"path" : "Observation.component.referenceRange.text",
"comment" : "MA: Andrew, do we support this?\r\n\r\nNote that FHIR strings SHALL NOT exceed 1MB in size",
"mustSupport" : true
}
]
},
"text" : {
}
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.